Skip to content

coredns: update to 1.14.2#59407

Open
al20ov wants to merge 1 commit intovoid-linux:masterfrom
al20ov:coredns-1.14.2
Open

coredns: update to 1.14.2#59407
al20ov wants to merge 1 commit intovoid-linux:masterfrom
al20ov:coredns-1.14.2

Conversation

@al20ov
Copy link
Contributor

@al20ov al20ov commented Mar 16, 2026

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-glibc

New release and I added go_build_tags=grpcnotrace because that's what coredns's Makefile builds with now: coredns/coredns@86d9bc7

Also had to ignore tests for coredns/plugin/trace on i686 since datadog-go triggers a panic: unaligned 64-bit atomic operation on 32 bit systems

@al20ov al20ov force-pushed the coredns-1.14.2 branch 2 times, most recently from 319f54c to 4766a8f Compare March 16, 2026 21:41
@Duncaen
Copy link
Member

Duncaen commented Mar 17, 2026

Sounds like the test is working.

@al20ov
Copy link
Contributor Author

al20ov commented Mar 19, 2026

@Duncaen you mean after the "fix"? Because without it, i686 doesn't pass: https://github.com/void-linux/void-packages/actions/runs/23167280243/job/67310474534

@Duncaen
Copy link
Member

Duncaen commented Mar 19, 2026

The point of tests is to identify issues, if we just disable all test that don't pass (for reasons besides the test being wrong) then we don't need to run tests.

@al20ov
Copy link
Contributor Author

al20ov commented Mar 19, 2026

I know it's clearly not ideal and not a real fix. What do you suggest? That I add a disclaimer in the template that the tracing plugin will be broken on i686? Or we disable building for i686 entirely? Or that I just drop the PR until/if this gets fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants